Systems and methods for ingesting data files using multi-threaded processing

ABSTRACT

In some instances, a method for ingesting data files is provided. The method comprises: obtaining, by an ingestion system associated with a distributed file system, a data file from an external data source; determining, by the ingestion system, a plurality of processing threads within the ingestion system to use to process the data file; determining, by the ingestion system, one or more offsets within the data file based on the plurality of determined processing threads; and ingesting, by the ingestion system, the data file by having each of the plurality of processing threads begin processing the data file at a plurality of different locations within the data file, wherein the plurality of different locations are associated with the one or more offsets.

BACKGROUND

A file system may receive many data files from many different sources.In some instances, these data files may be flat files such as a simpleplain text file or binary file. The size of the data files may impacthow fast the file system is able to ingest the data files. For example,typically, when the file system receives a data file (e.g., a data filefrom the LINUX file system), the file system (e.g., a HADOOP filesystem) may perform one or more operations (e.g., an “hdfs dfs -put”command) to convert this data file into an appropriate data fileassociated with the file system (e.g., convert the data file from LINUXfile system into a HADOOP data file) and ingest the data file. When thedata file is smaller in size, it may be fairly quick for the file systemto ingest this data file. However, the file system may have to ingestnumerous different data files that are typically substantial in size.Accordingly, with a large amount of data flowing into the file system,this may cause a bottleneck in the process of data ingestion.

Traditionally, by using the “hdfs dfs -put” command, the file system isable to transfer and ingest the contents of the data file using asingle-threaded process (e.g., a single processing thread of a device orprocessor such as a central processing unit (CPU)). Other methods thathave been used include splitting the file into multiple different piecessuch as by using a UNIX split command and then using the “hdfs dfs -put”command. However, the time it takes to actually split the data file intomultiple pieces is not instantaneous and in fact, may actually increasethe overall time taken to ingest a file. In particular, regardingsplitting the data files into separate data files and then ingesting thesplit data files, the overhead for this operation actually resides inthe process splitting the data files as the time taken to split a filephysically increases with the increase in file size. Accordingly, thereremains a technical need to rapidly ingest data files into the filesystem.

SUMMARY

In some examples, the present application may provide a way to ingest adata file (e.g., a flat file) in a multi-threaded fashion (e.g., byusing multiple different processing threads within a device orprocessor), which will lead to faster ingestion of the data files aswell as having to spend the overhead to physically split the file first.In some instances, the present application may create and/or generateoffsets within the data file using characteristics of the data file(e.g., by utilizing a command such as a RandomAccessFile class in JAVAto create offsets based on the row delimiter). These offsets may then beused to calculate the start points and number of bytes, which are thenpassed onto Channels in JAVA that are used to read, in parallel, thefile contents and ingest into them into the file system (e.g., theHADOOP file system). In some variations, the present application mayfurther determine a number of concurrent threads available to use toprocess the files in parallel such as determining the available threadswithin the device.

In one aspect, a method for ingesting data files is provided. The methodcomprises: obtaining, by an ingestion system associated with adistributed file system, a data file from an external data source;determining, by the ingestion system, a plurality of processing threadswithin the ingestion system to use to process the data file;determining, by the ingestion system, one or more offsets within thedata file based on the plurality of determined processing threads; andingesting, by the ingestion system, the data file by having each of theplurality of processing threads begin processing the data file at aplurality of different locations within the data file, wherein theplurality of different locations are associated with the one or moreoffsets.

Examples may include one of the following features, or any combinationthereof. For instance, in some examples, the determining the one or moreoffsets comprises: determining a number of row delimiters within thedata file; and determining the one or more offsets based on the numberof row delimiters.

In some instances, determining the plurality of processing threadswithin the ingestion system to use to process the data file comprisesdetermining a number of available processing threads for processing thedata file, and determining the one or more offsets is based on thenumber of row delimiters within the data file and the number ofavailable processing threads within the ingestion system.

In some variations, the method further comprises: capping a number ofprocessing threads used to ingest the data file at the determined numberof available processing threads; determining a new processing threadthat is available for processing the data file; and continuing to ingestthe data file based on the determined number of available processingthreads.

In some instances, determining the plurality of processing threadswithin the ingestion system to use to process the data file is based ona file size of the data file.

In some examples, ingesting the data file comprises: instructing a firstavailable processing thread, from the plurality of processing threads,to begin ingesting the data file at the beginning of the data file; andinstructing a second available processing thread, from the plurality ofprocessing threads, to begin ingesting the data file at a first offset,of the one or more offsets, within the data file.

In some variations, ingesting the data file further comprises:instructing a third available processing thread, from the plurality ofprocessing threads, to begin ingesting the data file at a second offset,of the one or more offsets, within the data file.

In some instances, the data file is a LINUX flat file. The distributedfile system is a HADOOP distributed file system. Further, ingesting thedata file is based on converting the LINUX flat file into a HADOOP datafile.

In some examples, determining the one or more offsets within the datafile comprises: populating entries of an offset array indicating theplurality of different locations within the data file for each of theplurality of processing threads begins processing the data file. Each ofthe entries of the offset array is based on a size of the data file andthe plurality of processing threads.

In some variations, populating the offset array comprises: determining aplurality of byte sizes to use for each of the entries of the offsetarray based on the size of the data file and the plurality of processingthreads; determining whether content at a byte size, of the plurality ofbyte sizes, indicates an end of a row of the data file; and based on thecontent at the byte size indicating the byte size is at the end of therow, storing the byte size in the offset array.

In some instances, populating the offset array further comprises: basedon the content at the byte size indicating the byte size is not at theend of the row, incrementing the byte size by one and determiningwhether second content at the incremented byte size indicates the end ofthe row; and based on the second content at the incremented byte sizeindicating the incremented byte size is at the end of the row, storingthe incremented byte size in the offset array.

In another aspect, a multi-threaded ingestion system comprises one ormore processors; and a non-transitory computer-readable medium havingprocessor-executable instructions stored thereon, wherein theprocessor-executable instructions, when executed, facilitate: obtaininga data file from an external data source; determining a plurality ofprocessing threads associated with the one or more processors to use toprocess the data file; determining one or more offsets within the datafile based on the plurality of determined processing threads; andingesting the data file by having each of the plurality of processingthreads begin processing the data file at a plurality of differentlocations within the data file, wherein the plurality of differentlocations are associated with the one or more offsets.

Examples may include one of the following features, or any combinationthereof. For example, in some instances, determining the one or moreoffsets comprises: determining a number of row delimiters within thedata file; and determining the one or more offsets based on the numberof row delimiters.

In some examples, determining the plurality of processing threads to useto process the data file comprises determining a number of availableprocessing threads for processing the data file, and determining the oneor more offsets is based on the number of row delimiters within the datafile and the number of available processing threads.

In some variations, the processor-executable instructions, whenexecuted, further facilitate: capping a number of processing threadsused to ingest the data file at the determined number of availableprocessing threads; determining a new processing thread that isavailable for processing the data file; and continuing to ingest thedata file based on the determined number of available processingthreads.

In some instances, determining the plurality of processing threads touse to process the data file is based on a file size of the data file.

In some examples, ingesting the data file comprises: instructing a firstavailable processing thread, from the plurality of processing threads,to begin ingesting the data file at the beginning of the data file; andinstructing a second available processing thread, from the plurality ofprocessing threads, to begin ingesting the data file at a first offset,of the one or more offsets, within the data file.

In some variations, ingesting the data file further comprises:instructing a third available processing thread, from the plurality ofprocessing threads, to begin ingesting the data file at a second offset,of the one or more offsets, within the data file.

In some instances, the data file is a LINUX flat file, and ingesting thedata file is based on converting the LINUX flat file into a HADOOP datafile.

In yet another aspect, a non-transitory computer-readable medium havingprocessor-executable instructions stored thereon, wherein theprocessor-executable instructions, when executed, facilitate: obtaininga data file from an external data source; determining a plurality ofprocessing threads within an ingestion system to use to process the datafile; determining one or more offsets within the data file based on theplurality of determined processing threads; and ingesting the data fileby having each of the plurality of processing threads begin processingthe data file at a plurality of different locations within the datafile, wherein the plurality of different locations are associated withthe one or more offsets.

All examples and features mentioned above may be combined in anytechnically possible way.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject technology will be described in even greater detail belowbased on the exemplary figures, but is not limited to the examples. Allfeatures described and/or illustrated herein can be used alone orcombined in different combinations. The features and advantages ofvarious examples will become apparent by reading the following detaileddescription with reference to the attached drawings which illustrate thefollowing:

FIG. 1 is a simplified block diagram depicting an exemplary computingenvironment in accordance with one or more examples of the presentapplication.

FIG. 2 is a simplified block diagram of one or more devices or systemswithin the exemplary environment of FIG. 1 .

FIG. 3 is an exemplary process for ingesting data files usingmulti-threaded processing in accordance with one or more examples of thepresent application.

FIG. 4 is another simplified block diagram depicting a multi-threadedingestion system in accordance with one or more examples of the presentapplication.

FIG. 5 is another simplified block diagram depicting the ingestion ofdata files into a storage system in accordance with one or more examplesof the present application.

DETAILED DESCRIPTION

Examples of the presented application will now be described more fullyhereinafter with reference to the accompanying FIGS, in which some, butnot all, examples of the application are shown. Indeed, the applicationmay be exemplified in different forms and should not be construed aslimited to the examples set forth herein; rather, these examples areprovided so that the application will satisfy applicable legalrequirements. Where possible, any terms expressed in the singular formherein are meant to also include the plural form and vice versa, unlessexplicitly stated otherwise. Also, as used herein, the term “a” and/or“an” shall mean “one or more” even though the phrase “one or more” isalso used herein. Furthermore, when it is said herein that something is“based on” something else, it may be based on one or more other thingsas well. In other words, unless expressly indicated otherwise, as usedherein “based on” means “based at least in part on” or “based at leastpartially on”.

Systems, methods, and computer program products are herein disclosedthat provide for ingesting data files using multi-threaded processing.FIG. 1 is a simplified block diagram depicting an exemplary environmentin accordance with an example of the present application. Theenvironment 100 includes one or more data sources 102, a distributedfile system 104, and a network 106. Although the entities withinenvironment 100 may be described below and/or depicted in the FIGS. asbeing singular entities, it will be appreciated that the entities andfunctionalities discussed herein may be implemented by and/or includeone or more entities.

The entities within the environment 100 such as the data sources 102 andthe distributed file system 104 may be in communication with othersystems within the environment 100 via the network 106. The network 106may be a global area network (GAN) such as the Internet, a wide areanetwork (WAN), a local area network (LAN), or any other type of networkor combination of networks. The network 106 may provide a wireline,wireless, or a combination of wireline and wireless communicationbetween the entities within the environment 100. Additionally, and/oralternatively, the data sources 102 may be in communication with thedistributed file system 104 without using the network 106. For instance,the data sources 102 may use one or more wired connections and/or one ormore communication protocols such as WI-FI or BLUETOOTH to communicatewith the distributed file system 104.

Each of the data sources 102 is and/or includes one or more computingdevices and/or systems that are configured to provide data (e.g., datafiles) to the distributed file system 104. For example, the data sources102 are and/or include one or more computing devices, computingplatforms, systems, servers, desktops, laptops, tablets, mobile devices(e.g., smartphone device, or other mobile device), or any other type ofcomputing device that generally comprises one or more communicationcomponents, one or more processing components, and one or more memorycomponents.

The data sources 102 are capable of performing tasks, functions, and/orother actions. For example, the data sources 102 may provide data suchas one or more data files to the distributed file system. The data filesmay be any type of data file that includes information. For example, insome variations, the data files may be a flat file, a comma-separatedvalue (CSV) file, a portable document format (PDF) file, a document(DOC) file, a compressed file (e.g., a ZIP file), an optimized rowcolumnar (ORC) file, a PARQUET file, an AVRO file, a JAVASCRIPT ObjectNotation (JSON) file, an extensible markup language (XML) file, and/oranother file type. The data file may include information and each of thedata sources 102 may provide one or more of these data files to thedistributed file system 104.

In some variations, the data sources 102 may be implemented as engines,software functions, and/or applications. In other words, thefunctionalities of the data sources 102 may be implemented as softwareinstructions stored in storage (e.g., memory) and executed by one ormore processors.

The distributed file system 104 is a computing system that is associatedwith an enterprise organization. The enterprise organization may be anytype of corporation, company, organization, and/or other institution. Insome examples, the distributed file system 104 is a HADOOP file system.In other words, the distributed filed system 104 operates using a HADOOPframework. The distributed file system 104 includes one or morecomputing devices, computing platforms, systems, servers, desktops,laptops, tablets, mobile devices (e.g., smartphone device, or othermobile device), or any other type of computing device that generallycomprises one or more communication components, one or more processingcomponents, and one or more memory components.

The distributed file system 104 is capable of performing tasks,functions, and/or other actions for the enterprise organization. Forexample, the distributed file system 104 includes a multi-threadedingestion system 108 that obtains (e.g., receives and/or retrieves) datafiles from the data sources 102. Then, the multi-threaded ingestionsystem 108 ingests the data files into the distributed file system 104using multiple different threads (e.g., processing threads or threads ofexecution). For example, the multi-threaded ingestion system 108 mayinclude one or more processors such as central processing units (CPUs).The processor may include one or more physical cores (e.g., CPU cores)or processing units, which are pieces of logic capable of independentperforming the functions of the processor. The physical cores mayinclude multiple different threads of execution that can executemultiple different tasks at one time. For instance, each of the threadsof execution may be executing programming code independent of eachother. By using multiple threads that executed at simultaneously (e.g.,multi-threaded processing), the processor may perform multiple tasks atthe same time. The multi-threaded ingestion system 108 may use multiplethreads to process each data file that is received from the data sources102. This will be described in further detail below.

In some instances, the data sources 102 may be using a first operatingsystem/framework such as a LINUX operating system and the distributedfile system 104 using a second framework such as a HADOOP framework.Using multiple different threads of execution, the multi-threadedingestion system 108 ingests the data files from the first operatingsystem/framework so that they are compatible with the second framework(e.g., the HADOOP framework). For instance, the multi-threaded ingestionsystem 108 provides instructions for each thread to read file charactersfrom the data file 412 and copy these characters into the distributedfile system 104.

In some examples, the multi-threaded ingestion system 108 maycreate/generate one or more offsets for ingesting the data file. Forexample, the multi-threaded ingestion system 108 may determine offsetswithin the data file based on characteristics of the data file (e.g.,delimiters such as row delimiters and/or the size of the data file). Forinstance, after each row within the data file, the data file may includeone or more characters such as “\n” to indicate the next row of the datafile. The one or more characters may be row delimiters. Themulti-threaded ingestion system 108 may determine an amount ofdelimiters (e.g., row delimiters) within the received data file. Then,based on the amount of delimiters and number of available processingthreads, the multi-threaded ingestion system 108 may generate one ormore offsets within the data file. After, the multi-threaded ingestionsystem 108 may use the generated offsets and the processing threads toingest the data file. For instance, a processing thread may beginingesting the data file at the beginning and each of the other availableprocessing threads may begin ingesting the data file at the generatedoffsets. Additionally, and/or alternatively, the multi-threadedingestion system 108 may generate the one or more offsets based on thesize of the data file (e.g., each thread may be tasked with ingesting anequal or substantially equal part of the data file).

In some variations, the distributed file system 104 may be implementedas engines, software functions, and/or applications. In other words, thefunctionalities of the distributed file system 104 may be implemented assoftware instructions stored in storage (e.g., memory) and executed byone or more processors.

It will be appreciated that the exemplary environment depicted in FIG. 1is merely an example, and that the principles discussed herein may alsobe applicable to other situations—for example, including other types ofinstitutions, organizations, devices, systems, and networkconfigurations. As will be described herein, the environment 100 may beused by health care enterprise organizations. However, in otherinstances, the environment 100 may be used by other types of enterpriseorganizations such as financial institutions or insurance institutions.

FIG. 2 is a block diagram of an exemplary system and/or device 200(e.g., the data sources 102, the distributed file system 104, and/or themulti-threaded ingestion system 108) within the environment 100. Thedevice/system 200 includes one or more processors 204, such as one ormore CPUs, controller, and/or logic, that executes computer executableinstructions for performing the functions, processes, and/or methodsdescribed herein. In some examples, the computer executable instructionsare locally stored and accessed from a non-transitory computer readablemedium, such as storage 210, which may be a hard drive or flash drive.Read Only Memory (ROM) 206 includes computer executable instructions forinitializing the processor 204, while the random-access memory (RAM) 208is the main memory for loading and processing instructions executed bythe processor 204. The network interface 212 may connect to a wirednetwork or cellular network and to a local area network or wide areanetwork, such as the network 106. The device/system 200 may also includea bus 202 that connects the processor 204, ROM 206, RAM 208, storage210, and/or the network interface 212. The components within thedevice/system 200 may use the bus 202 to communicate with each other.The components within the device/system 200 are merely exemplary andmight not be inclusive of every component, server, device, computingplatform, and/or computing apparatus within the device/system 200. Forexample, the distributed file system 104 and the multi-threadedingestion system 108 may include some of the components within thedevice/system 200 and may also include additional and/or alternativecomponents. Additionally, and/or alternatively, the device/system 200may further include components that might not be included within everyentity of environment 100.

FIG. 3 is an exemplary process 300 for ingesting data files usingmulti-threaded processing in accordance with one or more examples of thepresent application. The process 300 may be performed by the distributedfile system 104 and/or the multi-threaded ingestion system 108 ofenvironment 100 shown in FIG. 1 . However, it will be recognized thatthe process 300 may be performed in any suitable environment and thatany of the following blocks may be performed in any suitable order.

FIG. 4 is a simplified block diagram depicting the multi-threadedingestion system 108 in accordance with one or more examples of thepresent application and will be used to describe process 300 in moredetail. In particular, the multi-threaded ingestion system 108 includesthe network interface 404, a first processor (e.g., CPU) 406, and memory410. Optionally, which is denoted by the dotted lines, themulti-threaded ingestion system 108 further includes a second processor416. The network interface 404 may be and/or have similar functionalityto the network interface 212. For example, the multi-threaded ingestionsystem 108 may use the network interface 404 to communicate with otherentities within the environment 100. For instance, the multi-threadedingestion system 108 may receive information 402 such as the data files(e.g., flat files) from the data sources 102 either directly, via thenetwork 106, and/or via other devices.

The first processor 406 may include a plurality of first processingthreads 408 (e.g., a plurality of threads of execution). As mentionedabove, the first processor 406 may be a CPU that includes one or moreprocessing cores. The processing cores may include threads of executionsuch as the plurality of processing threads 408. The plurality of firstprocessing threads 408 may perform functions for the first processor 406such as ingesting the data files that are received from the data sources102.

The memory 410 may be and/or include a computer-usable orcomputer-readable medium such as, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductorcomputer-readable medium. More specific examples (e.g., a non-exhaustivelist) of the computer-readable medium may include the following: anelectrical connection having one or more wires; a tangible medium suchas a portable computer diskette, a hard disk, a time-dependent accessmemory (RAM such as the RAM 208), a ROM such as ROM 206, an erasableprogrammable read-only memory (EPROM or Flash memory), a compact discread-only memory (CD_ROM), or other tangible optical or magnetic storagedevice. The computer-readable medium may store computer-readableinstructions 414/program code for carrying out operations of the presentapplication. For example, when executed by the first and/or secondprocessors 406 and 416, the computer-readable instructions/program codemay carry out operations described herein.

The memory 410 may further store the data files 412 that are receivedfrom the data sources 102. For example, after receiving the data files412, the multi-threaded ingestion system 108 (e.g., the first processor406) may store the data files 412 in memory 410. Then, as will beexplained below, the first and/or second processors 406 and/or 416 mayuse their processing threads 408 and/or 418 to ingest the data files 412that are stored in memory 410.

The second processor 416, when present, may include a plurality ofsecond processing threads 418. The second processor 416, including thesecond processing threads 418, may operate similarly to the firstprocessor 406 and the first processing threads 408. In other words, thesecond processing threads 418 may be used to ingest the data files 412that are received from the data sources 102. Only two processors (e.g.,first and second processors 406 and 416) are shown in FIG. 4 solely forclarity and brevity, and the multi-threaded ingestion system 108 mayinclude numerous processors and each of these processors may includetheir own processing threads that may be used to ingest the data files412.

The descriptions, illustrations, entities, and processes of FIGS. 3 and4 are merely exemplary and the process 300 and/or the multi-threadedingestion system 108 may use other descriptions, illustrations, andprocesses for ingesting data files using multi-threaded processing.

Referring back to FIG. 3 , in operation, at block 302, themulti-threaded ingestion system 108 obtains (e.g., receives and/orretrieves) a data file from an external data source such as the one ormore data sources 102. For example, using the network interface 404, themulti-threaded ingestion system 108 may receive information 402 such asone or more data files 412. In some instances, the multi-threadedingestion system 108 may store the data file 412 in memory 410. Afterstoring the data file 412 in memory 410, the multi-threaded ingestionsystem 108 may ingest the data file 412, which is described below inblocks 304-308. In other instances, the multi-threaded ingestion system108 may begin ingesting the data files 412 without storing the files 412in memory 410 first.

In some examples, the data file may be a flat file and/or in anotherfile format as described above. Additionally, and/or alternatively, thedata file may be in a first framework such as a LINUX framework and thedistributed file system 104 that includes the multi-threaded ingestionsystem 108 may be in another framework such as a HADOOP framework.

At block 304, the multi-threaded ingestion system 108 determines aplurality of processing threads within the ingestion system 108 to useto process (e.g., ingest) the data file. For instance, themulti-threaded ingestion system 108 may determine a number of processingthreads (e.g., from the first and/or second processing threads 408 and418 of the first and/or second processors 406 and 416) to use to ingestthe data file 412 that was obtained at block 302.

In some instances, the multi-threaded ingestion system 108 may determinethe plurality of processing threads to use for ingesting the data filebased on determining a number of available processing threads that arewithin the multi-threaded ingestion system 108. The available processingthreads may be threads that are available and able to used for ingestingthe data file 412. For instance, one or more of the processing threads(e.g., the threads 408 and/or 418) may be executing other operations andnot available (e.g., not idle). For example, two or more data files maybe ingested by the multi-threaded ingestion system 108 at the same time.The first data file may be ingested using a first subset of processingthreads from the threads 408 and/or 418. These first subset ofprocessing threads might not be available for ingesting the second datafile (e.g., the data file 412). Therefore, the multi-threaded ingestionsystem 108 may determine the processing threads that are available foringestion of the data file 412 (e.g., the threads that are not beingused to ingest the first data file and/or executing other applications,programs, and/or instructions). In some examples, the multi-threadedingestion system 108 may use one or more commands and/or logic todetermine (e.g., calculate) the number of processing threads within themulti-threaded ingestion system 108 and/or the number of processingthreads that are available at that point in time to use to ingest thedata file 412.

In some variations, the multi-threaded ingestion system 108 maydetermine the plurality of processing threads to use for ingesting thedata file 412 based on the size of the data file 412. For example, basedon comparing the size of the data file 412 with one or more thresholds,the multi-threaded ingestion system 108 may determine the number ofprocessing threads to use for ingesting the data file 412. For instance,based on the data file size being under 128 megabytes (MB), themulti-threaded ingestion system 108 may use one processing thread foringesting the data file. Based on the data file size being between 128MB and 256 MB, the multi-threaded ingestion system 108 may use twoprocessing threads. Based on the data file size being between 256 MB and384, the multi-threaded ingestion system 108 may use three processingthreads, and so on.

In some instances, the multi-threaded ingestion system 108 may use boththe size of the data file 412 as well as the number of availableprocessing threads to determine the plurality of processing threads touse for ingesting the data file 412. For instance, based on the datafile size, the multi-threaded ingestion system 108 may determine to usea number of threads such as five threads. The multi-threaded ingestionsystem 108 may determine, however, that only four threads are available.Therefore, the multi-threaded ingestion system 108 may compare these twovalues and may determine the plurality of processing threads to use foringesting the data file 412 based on the lower value and/or anothermetric.

At block 306, the multi-threaded ingestion system 108 determines one ormore offsets within the data file based on the plurality of determinedprocessing threads. For example, the multi-threaded ingestion system 108may use one or more characteristics of the data file 412 to determinethe location of the one or more offsets. For instance, as mentionedabove, the data file 412 may include a plurality of row delimiters(e.g., the characters “\n”), which may appear after each row of the datafile 412. The multi-threaded ingestion system 108 may determine thenumber of these row delimiters within the data file 412. Then, based onthe number of the row delimiters and the number of processing threads toprocess the data file 412, which was determined at block 304, themulti-threaded ingestion system 108 may determine the number of offsetsto use for the data file 412 as well as the locations of these offsetswithin the data file 412. For example, the multi-threaded ingestionsystem 108 may determine there are 1,000 row delimiters (e.g., 1,000rows) within the data file 412 and five processing threads to use toprocess the data file 412. Based on these numbers, the multi-threadedingestion system 108 may determine to use four offsets (e.g., the fiveprocessing threads minus the one processing thread that begins at thebeginning of the data file 412) and that the location of these offsetswithin the data file 412 should be at the 200 row mark, 400 row mark,600 row mark, and 800 row mark.

In some instances, the multi-threaded ingestion system 108 may generateand/or create one or more pointers at the locations of these offsets.For instance, referring to the example above, the multi-threadedingestion system 108 may generate four pointers—one at the 200 row mark,one at the 400 row mark, one at the 600 row mark, and one at the 800 rowmark.

At block 308, the multi-threaded ingestion system 108 ingests the datafile by having each of the plurality of processing threads beginprocessing the data file at a plurality of locations within the datafile 412. The plurality of different locations are associated with theone or more offsets. For example, the multi-threaded ingestion system108 may ingest the data file 412 using the determined offsets from block306. For instance, the multi-threaded ingestion system 108 may provideone or more instructions and/or commands to the first processing thread,of the plurality of determined processing threads, to begin ingestingthe data file 412 at the beginning of the data file 412. Further, themulti-threaded ingestion system 108 may provide one or more instructionsto the second processing thread to begin ingesting the data file 412 atthe location of the first offset (e.g., at the 200 row mark), the thirdprocessing thread to begin ingesting the data file 412 at the locationof the second offset (e.g., at the 400 row mark), and so on.

In other words, the multi-threaded ingestion system 108 determines anumber of processing threads to use to ingest the data file 412 andoffsets within the data file 412 to use for the processing threads. Themulti-threaded ingestion system 108 then begins ingesting the filesusing the offsets such that a different processing thread beginsingesting the data file 412 at each of the offsets. By using thesedifferent offsets and processing threads, the multi-threaded ingestionsystem 108 is capable of increasing the speed at which the data file 412is ingested within the distributed file system 104.

In some instances, the multi-threaded ingestion system 108 may ingestthe data file 412 using multiple files so as to avoid a file lock. Forinstance, a file lock may be when a file system does not allow multipleprocesses to write into the same file at the same time. To avoid thefile lock, the multi-threaded ingestion system 108 may use multipledifferent processing threads to write to multiple different “part” files(e.g., files with different names). For example, the processing threadsmay be ingesting the data file 412, and each of the threads may bewriting the information from the data file 412 into a different “part”file.

In some examples, after the data file 412 has already begun beingingested (e.g., after block 308), the multi-threaded ingestion system108 may re-assess the number of processing threads (e.g., processingthreads 408 and/or 418) to use to ingest the data file 412. In otherexamples, the multi-threaded ingestion system 108 may set the maximumnumber of processing threads to use to ingest the file as the number ofprocessing threads that was determined at block 304. For example, atblock 304, the multi-threaded ingestion system 108 may determine acertain number of processing threads (e.g., five threads). Then, afterblock 308 and the beginning of the ingestion process, the multi-threadedingestion system 108 may determine one or more new processing threadsthat has become available. For instance, as mentioned above, themulti-threaded ingestion system 108 may be ingesting multiple differentdata files. After one of these data files has been completed, then theprocessing threads that are used to process this data file may becomeavailable. However, after block 308 and after the ingestion processbegins, the multi-threaded ingestion system 108 might not use the newlyavailable processing threads to process the data file.

In some variations, the multi-threaded ingestion system 108 determinesthe offsets based on the size of the data file 412 and the determinedprocessing threads to use to process the data file 412 from block 304.For example, the data file 412 may be 500 bytes and at block 304, themulti-threaded ingestion system 108 may determine to use four processingthreads for processing the data file 412. The multi-threaded ingestionsystem 108 may generate and/or create an offset array with four slots.Each of these slots indicates a location (e.g., a pointer) within thedata file 412 for one of the four processing threads to begin ingestingthe data file 412. For instance, the first slot may be zero, whichindicates that the first processing thread begins at the beginning ofthe data file 412.

The multi-threaded ingestion system 108 may traverse through the file topopulate the rest of the offset array. For instance, the multi-threadedingestion system 108 may determine a byte value for one of theprocessing threads to begin ingesting the data file 412 based on thesize of the data file 412 and the determined processing threads. Forexample, the multi-threaded ingestion system 108 may seek for each ofthe processing threads to process a similar amount of data from the datafile 412. Thus, based on the determined processing threads being fourand the size of the data file 412 being 500 bytes, the multi-threadedingestion system 108 may determine the offsets as multiples of 125 bytes(e.g., 500 bytes divided by four).

In some instances, the determined byte value for one of the processingthreads to begin ingesting the data file 412 may be in the middle of therow or at the end of the data file 412 and the multi-threaded ingestionsystem 108 may attempt to keep each of the rows together. As such, themulti-threaded ingestion system 108 may check whether the dataassociated with the byte value (e.g., the content within the data file412 at the byte value) indicates an end of the row (e.g., the “\n”character as described above) and/or an end of the file (e.g., a “−1”character). Based on the content at the byte value indicating the end ofthe row or end of the file, the multi-threaded ingestion system 108 maypopulate the byte value (e.g., 125) into the offset array. Based on thecontent at the byte value not indicating the end of the row or end ofthe file, the multi-threaded ingestion system 108 may move onto the nextbyte value and check whether the data (e.g., content) at the next bytevalue indicates an end of row or end of file. The multi-threadedingestion system 108 may continue with moving onto the next byte andchecking whether the next byte value indicates an end of row or end offile until it reaches the end of the row or the end of the file. Then,the multi-threaded ingestion system 108 may populate this byte valueinto the offset array.

After populating the entries of the offset array, the process 300 maymove to block 308 and the multi-threaded ingestion system 108 may ingestthe data file 412 using the entries of the array. For instance, theoffset array may indicate 0 bytes, 133 bytes, 277 bytes, and 415 bytes.Each of the processing threads may begin ingesting the data file 412 atthose byte markers.

In other words, each of the rows of the data file 412 may be differentsizes (e.g., byte sizes). For instance, the first row may have more datathan the second row and as such, the first row may be ten bytes whereasthe second row may be five bytes. Accordingly, in some examples, ratherthan ingesting the data file 412 by rows as described above, themulti-threaded ingestion system 108 may ingest the data file 412 basedon the rows as well as actual file size of data file 412.

FIG. 5 shows another simplified block diagram 500 depicting theingestion of data files into a storage system in accordance with one ormore examples of the present application. For example, the block diagram500 shows a data file 502 to be ingested into the storage system 506 ofthe distributed file system 104 using the multi-threaded processingdescribed above. The multi-threaded ingestion system 108 may determinethe number of processing threads (e.g., ten) to use for ingesting thedata file as well as the offsets for the processing threads.

Then, at block 308, the multi-threaded ingestion system 108 may ingestthe data file 502. For example, the multi-threaded ingestion system 108may use a parallel copy code 504 that copies and/or performs otheroperations in order to ingest the data file 412 into the storage system506. As shown, the multi-threaded ingestion system 108 may use the tendetermined threads to both copy the data file 502 as well as to storethe contents within the storage system 506. The storage system 506 maybe and/or include a computer-usable or computer-readable medium such as,but not limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor computer-readable medium. More specificexamples (e.g., a non-exhaustive list) of the computer-readable mediummay include the following: an electrical connection having one or morewires; a tangible medium such as a portable computer diskette, a harddisk, a time-dependent access memory (RAM such as the RAM 208), a ROMsuch as ROM 206, an erasable programmable read-only memory (EPROM orFlash memory), a compact disc read-only memory (CD_ROM), or othertangible optical or magnetic storage device.

In some variations, the parallel copy code 504 may calculate a number ofrows within the data file 502, determine the memory and number ofthreads available within the multi-threaded ingestion system 108 to usefor ingesting the data file 502, create offsets in the data file 502 tofeed to each of the threads (e.g., calculating offsets using rowdelimiters and/or ensuring the data contents/words are not split intopieces), enable each individual thread to operate in parallel andconsume/write its respective chunk of data into the storage system 506,and/or stop the processing threads after the thread has finished copyingits portion of the data file 502 such that the memory may be releasedback to the multi-threaded ingestion system 108 for use in ingestinganother data file and/or other operations.

In some instances, the data file (e.g., 412 and/or 502) may be acompressed file such as a ZIP file. The multi-threaded ingestion system108 may ingest the compressed file with or without decompressing thefile first. For instance, the multi-threaded ingestion system 108 mayingest the compressed file without decompressing the file first, whichmay assist in achieving faster file ingestions.

In some examples, the multi-threaded ingestion system 108 may stichfiles together into a single file and then ingest the single file usingprocess 300. For instance, the multi-threaded ingestion system 108 mayuse a MapReduce program to merge multiple files together into one fileprior to ingesting the file.

In some variations, the multi-threaded ingestion system 108 may performfile level changes (e.g., a “sed” command on UNIX) prior to ingestingthe data file. For instance, the file level changes may include changesto the column delimiter, remove special characters that may not bereadable by the file ingestion system 104 (e.g., the HADOOP fileingestion system), and/or add/remove header and trailer records.

A number of implementations have been described. Nevertheless, it willbe understood that additional modifications may be made withoutdeparting from the scope of the inventive concepts described herein,and, accordingly, other examples are within the scope of the followingclaims. For example, it will be appreciated that the examples of theapplication described herein are merely exemplary. Variations of theseexamples may become apparent to those of ordinary skill in the art uponreading the foregoing description. The inventor expects skilled artisansto employ such variations as appropriate, and the inventor intends forthe application to be practiced otherwise than as specifically describedherein. Accordingly, this application includes all modifications andequivalents of the subject matter recited in the claims appended heretoas permitted by applicable law. Moreover, any combination of theabove-described elements in all possible variations thereof isencompassed by the application unless otherwise indicated herein orotherwise clearly contradicted by context.

It will further be appreciated by those of skill in the art that theexecution of the various machine-implemented processes and stepsdescribed herein may occur via the computerized execution ofprocessor-executable instructions stored on a non-transitorycomputer-readable medium, e.g., random access memory (RAM), read-onlymemory (ROM), programmable read-only memory (PROM), volatile,nonvolatile, or other electronic memory mechanism. Thus, for example,the operations described herein as being performed by computing devicesand/or components thereof may be carried out by according toprocessor-executable instructions and/or installed applicationscorresponding to software, firmware, and/or computer hardware.

The use of the term “at least one” followed by a list of one or moreitems (for example, “at least one of A and B”) is to be construed tomean one item selected from the listed items (A or B) or any combinationof two or more of the listed items (A and B), unless otherwise indicatedherein or clearly contradicted by context. The terms “comprising,”“having,” “including,” and “containing” are to be construed asopen-ended terms (i.e., meaning “including, but not limited to,”) unlessotherwise noted. Recitation of ranges of values herein are merelyintended to serve as a shorthand method of referring individually toeach separate value falling within the range, unless otherwise indicatedherein, and each separate value is incorporated into the specificationas if it were individually recited herein. All methods described hereincan be performed in any suitable order unless otherwise indicated hereinor otherwise clearly contradicted by context. The use of any and allexamples, or exemplary language (e.g., “such as”) provided herein, isintended merely to better illuminate the application and does not pose alimitation on the scope of the application unless otherwise claimed. Nolanguage in the specification should be construed as indicating anynon-claimed element as essential to the practice of the application.

The invention claimed is:
 1. A method for ingesting data files,comprising: obtaining, by an ingestion system associated with adistributed file system, a data file from an external data source;determining, by the ingestion system, a plurality of processing threadswithin the ingestion system to use to process the data file;determining, by the ingestion system, one or more offsets within thedata file, wherein determining the one or more offsets within the datafile comprises populating entries of an offset array indicating aplurality of different locations within the data file for each of theplurality of processing threads to begin processing the data file,wherein each of the entries of the offset array is based on a size ofthe data file, the plurality of processing threads, and a row delimiterindicating an end of a row of the data file; and ingesting, by theingestion system, the data file by having each of the plurality ofprocessing threads begin processing the data file at the plurality ofdifferent locations within the data file, wherein the plurality ofdifferent locations are associated with the one or more offsets, andwherein populating the entries of the offset array comprises:determining a plurality of byte sizes to use for each of the entries ofthe offset array based on the size of the data file and the plurality ofprocessing threads; determining whether content at a byte size, of theplurality of byte sizes, indicates the row delimiter; and based on thecontent at the byte size indicating the byte size is at the rowdelimiter, storing the byte size in the offset array.
 2. The method ofclaim 1, wherein determining the plurality of processing threads withinthe ingestion system to use to process the data file comprisesdetermining a number of available processing threads for processing thedata file, and wherein determining the one or more offsets is furtherbased on the number of available processing threads within the ingestionsystem.
 3. The method of claim 2, further comprising: capping a numberof processing threads used to ingest the data file at the determinednumber of available processing threads; determining a new processingthread that is available for processing the data file; and continuing toingest the data file based on the determined number of availableprocessing threads.
 4. The method of claim 1, wherein ingesting the datafile comprises: instructing a first available processing thread, fromthe plurality of processing threads, to begin ingesting the data file atthe beginning of the data file; and instructing a second availableprocessing thread, from the plurality of processing threads, to beginingesting the data file at a first offset, of the one or more offsets,within the data file.
 5. The method of claim 4, wherein ingesting thedata file further comprises: instructing a third available processingthread, from the plurality of processing threads, to begin ingesting thedata file at a second offset, of the one or more offsets, within thedata file.
 6. The method of claim 1, wherein ingesting the data file isbased on converting the data file into a HADOOP data file.
 7. The methodof claim 1, wherein populating the entries of the offset array furthercomprises: based on the content at the byte size indicating the bytesize is not the row delimiter, incrementing the byte size by one anddetermining whether second content at the incremented byte sizeindicates the row delimiter; and based on the second content at theincremented byte size indicating the incremented byte size is the rowdelimiter, storing the incremented byte size in the offset array.
 8. Amulti-threaded ingestion system, comprising: one or more processors; anda non-transitory computer-readable medium having processor-executableinstructions stored thereon, wherein the processor-executableinstructions, when executed, facilitate: obtaining a data file from anexternal data source; determining a plurality of processing threadsassociated with the one or more processors to use to process the datafile; determining one or more offsets within the data file, whereindetermining the one or more offsets within the data file comprisespopulating entries of an offset array indicating a plurality ofdifferent locations within the data file for each of the plurality ofprocessing threads to begin processing the data file, wherein each ofthe entries of the offset array is based on a size of the data file, theplurality of processing threads, and a row delimiter indicating an endof a row of the data file; and ingesting the data file by having each ofthe plurality of processing threads begin processing the data file atthe plurality of different locations within the data file, wherein theplurality of different locations are associated with the one or moreoffsets, and wherein populating the entries of the offset arraycomprises: determining a plurality of byte sizes to use for each of theentries of the offset array based on the size of the data file and theplurality of processing threads; determining whether content at a bytesize, of the plurality of byte sizes, indicates the row delimiter; andbased on the content at the byte size indicating the byte size is at therow delimiter, storing the byte size in the offset array.
 9. Themulti-threaded ingestion system of claim 8, wherein determining theplurality of processing threads to use to process the data filecomprises determining a number of available processing threads forprocessing the data file, and wherein determining the one or moreoffsets is further based on the number of available processing threads.10. The multi-threaded ingestion system of claim 9, wherein theprocessor-executable instructions, when executed, further facilitate:capping a number of processing threads used to ingest the data file atthe determined number of available processing threads; determining a newprocessing thread that is available for processing the data file; andcontinuing to ingest the data file based on the determined number ofavailable processing threads.
 11. The multi-threaded ingestion system ofclaim 8, wherein ingesting the data file comprises: instructing a firstavailable processing thread, from the plurality of processing threads,to begin ingesting the data file at the beginning of the data file; andinstructing a second available processing thread, from the plurality ofprocessing threads, to begin ingesting the data file at a first offset,of the one or more offsets, within the data file.
 12. The multi-threadedingestion system of claim 11, wherein ingesting the data file furthercomprises: instructing a third available processing thread, from theplurality of processing threads, to begin ingesting the data file at asecond offset, of the one or more offsets, within the data file.
 13. Themulti-threaded ingestion system of claim 8, wherein ingesting the datafile is based on converting the data file into a HADOOP data file. 14.The multi-threaded ingestion system of claim 8, wherein populating theentries of the offset array further comprises: based on the content atthe byte size indicating the byte size is not the row delimiter,incrementing the byte size by one and determining whether second contentat the incremented byte size indicates the row delimiter; and based onthe second content at the incremented byte size indicating theincremented byte size is the row delimiter, storing the incremented bytesize in the offset array.
 15. A non-transitory computer-readable mediumhaving processor-executable instructions stored thereon, wherein theprocessor-executable instructions, when executed, facilitate: obtaininga data file from an external data source; determining a plurality ofprocessing threads within an ingestion system to use to process the datafile; determining one or more offsets within the data file, whereindetermining the one or more offsets within the data file comprisespopulating entries of an offset array indicating a plurality ofdifferent locations within the data file for each of the plurality ofprocessing threads to begin processing the data file, wherein each ofthe entries of the offset array is based on a size of the data file, theplurality of processing threads, and a row delimiter indicating an endof a row of the data file; and ingesting the data file by having each ofthe plurality of processing threads begin processing the data file atthe plurality of different locations within the data file, wherein theplurality of different locations are associated with the one or moreoffsets, and wherein populating the entries of the offset arraycomprises: determining a plurality of byte sizes to use for each of theentries of the offset array based on the size of the data file and theplurality of processing threads; determining whether content at a bytesize, of the plurality of byte sizes, indicates the row delimiter; andbased on the content at the byte size indicating the byte size is at therow delimiter, storing the byte size in the offset array.
 16. Thenon-transitory computer-readable medium of claim 15, wherein populatingthe entries of the offset array further comprises: based on the contentat the byte size indicating the byte size is not the row delimiter,incrementing the byte size by one and determining whether second contentat the incremented byte size indicates the row delimiter; and based onthe second content at the incremented byte size indicating theincremented byte size is the row delimiter, storing the incremented bytesize in the offset array.
 17. The non-transitory computer-readablemedium of claim 15, wherein determining the plurality of processingthreads within the ingestion system to use to process the data filecomprises determining a number of available processing threads forprocessing the data file, and wherein determining the one or moreoffsets is further based on the number of available processing threadswithin the ingestion system.
 18. The non-transitory computer-readablemedium of claim 17, wherein the processor-executable instructions, whenexecuted, further facilitate: capping a number of processing threadsused to ingest the data file at the determined number of availableprocessing threads; determining a new processing thread that isavailable for processing the data file; and continuing to ingest thedata file based on the determined number of available processingthreads.
 19. The non-transitory computer-readable medium of claim 15,wherein ingesting the data file comprises: instructing a first availableprocessing thread, from the plurality of processing threads, to beginingesting the data file at the beginning of the data file; andinstructing a second available processing thread, from the plurality ofprocessing threads, to begin ingesting the data file at a first offset,of the one or more offsets, within the data file.
 20. The non-transitorycomputer-readable medium of claim 15, wherein ingesting the data file isbased on converting the data file into a HADOOP data file.